Enter a type and click search.




Results for Magento\Payment\Gateway\Config\Config

File: vendor/klarna/module-kp/etc/di.xml

<virtualType name="KPConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            Klarna\Kp\Model\Payment\Kp::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual KPConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a KPConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = Klarna\Kp\Model\Payment\Kp::METHOD_CODE;
Results for Magento\Payment\Gateway\Config\Config

File: vendor/magento/module-paypal/etc/di.xml

<virtualType name="PayflowProVaultPaymentConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            Magento\Paypal\Model\Payflow\Transparent::CC_VAULT_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual PayflowProVaultPaymentConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a PayflowProVaultPaymentConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = Magento\Paypal\Model\Payflow\Transparent::CC_VAULT_CODE;
Results for Magento\Payment\Gateway\Config\Config

File: vendor/magento/magento2-base/dev/tests/integration/_files/Magento/TestModuleFakePaymentMethod/etc/di.xml

<virtualType name="Magento\TestModuleFakePaymentMethod\Gateway\Config\Config"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="string">
            fake
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual Magento\TestModuleFakePaymentMethod\Gateway\Config\Config object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a Magento\TestModuleFakePaymentMethod\Gateway\Config\Config object that the following arguments should be used in the foo object's constructor.

  • $methodCode = "fake";

File: vendor/magento/magento2-base/dev/tests/integration/_files/Magento/TestModuleFakePaymentMethod/etc/di.xml

<virtualType name="Magento\TestModuleFakePaymentMethod\Gateway\Config\Vault\Config"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="string">
            fake_vault
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual Magento\TestModuleFakePaymentMethod\Gateway\Config\Vault\Config object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a Magento\TestModuleFakePaymentMethod\Gateway\Config\Vault\Config object that the following arguments should be used in the foo object's constructor.

  • $methodCode = "fake_vault";
Results for Magento\Payment\Gateway\Config\Config

File: vendor/magento/module-vault/etc/di.xml

<type name="Magento\Vault\Model\Method\Vault">
    <arguments>
        <argument name="config" xsi:type="object">
            Magento\Payment\Gateway\Config\Config
        </argument>
        <argument name="valueHandlerPool" xsi:type="object">
            VaultPaymentValueHandlerPool
        </argument>
        <argument name="vaultProvider" xsi:type="object">
            Magento\Vault\Model\Method\NullPaymentProvider
        </argument>
        <argument name="code" xsi:type="string">
            vault
        </argument>
    </arguments>
</type>

This is a type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This configuration tells the Object Manager that when a user wants a Magento\Vault\Model\Method\Vault object that the following arguments should be used in the foo object's constructor.

File: vendor/magento/module-vault/etc/di.xml

<virtualType name="VaultPaymentDefaultValueHandler"
             type="Magento\Payment\Gateway\Config\ConfigValueHandler">
    <arguments>
        <argument name="configInterface" xsi:type="object">
            Magento\Payment\Gateway\Config\Config
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual VaultPaymentDefaultValueHandler object that it should return a Magento\Payment\Gateway\Config\ConfigValueHandler object.

This configuration tells the Object Manager that when a user wants a VaultPaymentDefaultValueHandler object that the following arguments should be used in the foo object's constructor.

Results for Magento\Payment\Gateway\Config\Config

File: vendor/magento/module-payment/etc/di.xml

<type name="Magento\Payment\Block\ConfigurableInfo">
    <arguments>
        <argument name="config" xsi:type="object">
            Magento\Payment\Gateway\Config\Config
        </argument>
    </arguments>
</type>

This is a type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This configuration tells the Object Manager that when a user wants a Magento\Payment\Block\ConfigurableInfo object that the following arguments should be used in the foo object's constructor.

Results for Magento\Payment\Gateway\Config\Config

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeVaultPaymentConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\Ui\ConfigProvider::CC_VAULT_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeVaultPaymentConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeVaultPaymentConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\Ui\ConfigProvider::CC_VAULT_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreePayPalVaultPaymentConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\Ui\PayPal\ConfigProvider::PAYPAL_VAULT_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreePayPalVaultPaymentConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreePayPalVaultPaymentConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\Ui\PayPal\ConfigProvider::PAYPAL_VAULT_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeApplePayConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\ApplePay\Ui\ConfigProvider::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeApplePayConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeApplePayConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\ApplePay\Ui\ConfigProvider::METHOD_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeGooglePayConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\GooglePay\Ui\ConfigProvider::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeGooglePayConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeGooglePayConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\GooglePay\Ui\ConfigProvider::METHOD_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeVenmoConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\Venmo\Ui\ConfigProvider::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeVenmoConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeVenmoConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\Venmo\Ui\ConfigProvider::METHOD_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeAchConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\Ach\Ui\ConfigProvider::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeAchConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeAchConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\Ach\Ui\ConfigProvider::METHOD_CODE;

File: vendor/paypal/module-braintree-core/etc/di.xml

<virtualType name="BraintreeLpmConfig"
             type="Magento\Payment\Gateway\Config\Config">
    <arguments>
        <argument name="methodCode" xsi:type="const">
            PayPal\Braintree\Model\Lpm\Ui\ConfigProvider::METHOD_CODE
        </argument>
    </arguments>
</virtualType>

This is a virtual type configuration.

This configuration is for the base area. Base area configurations will apply to all the sub-applications.

This virtualType configuration tells the Object Manager when a user wants a virtual BraintreeLpmConfig object that it should return a Magento\Payment\Gateway\Config\Config object.

This configuration tells the Object Manager that when a user wants a BraintreeLpmConfig object that the following arguments should be used in the foo object's constructor.

  • $methodCode = PayPal\Braintree\Model\Lpm\Ui\ConfigProvider::METHOD_CODE;